chore(mcp): drop 24 narrow tools from user-facing MCP surface#142
Merged
Conversation
The v0.3.0 release exposed 34 MCP tools — 6 consolidated mode-driven plus 28 narrow tools (20 graph + 9 topology + 4 intelligence, minus run_cypher / read_file / generate_flow / review_changes which stay). Greenfield project, no pinned consumers — drop the 24 narrow tools that the consolidated layer subsumes from the MCP surface. Surface drops 34 -> 10: - 6 consolidated (graph_summary, find_in_graph, inspect_node, trace_relationships, analyze_impact, topology_view) - 4 first-class (run_cypher, read_file, generate_flow, review_changes) Implementation: keep all toolXxx(d) Tool builder functions in tools_graph.go / tools_intelligence.go / tools_topology.go because tools_consolidated.go delegates to them at the Go-API level for mode dispatch. RegisterGraph / RegisterIntelligence / RegisterTopology remain available for unit tests that exercise narrow tool behavior directly. Production cli wiring (registerAllTools) now calls a new RegisterGraphUserFacing that registers only run_cypher + read_file. Doc sweep: CLAUDE.md, README.md, PROJECT_SUMMARY.md updated to reflect the 10-tool surface; integration_test.go updated to assert 10 and spot-check the consolidated names.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Architectural note
The narrow `toolXxx(d) Tool` builder funcs in `tools_graph.go` / `tools_intelligence.go` / `tools_topology.go` stay because `tools_consolidated.go` delegates to them at the Go-API level for mode dispatch. `RegisterGraph` / `RegisterIntelligence` / `RegisterTopology` remain available for unit tests that exercise narrow tool behavior directly; only the production cli wiring switches to the slim `RegisterGraphUserFacing` helper (run_cypher + read_file only).
Test plan
Coordination
Part of the parallel backlog cleanup (PRs #139, #140, #141, this one). #139 touches `tools_consolidated_test.go`, this PR touches `tools_graph.go` / `tools_graph_test.go` — minor rebase only at merge time.